Onboarding Prerequisites

The following table summarizes the actions to perform for setting up the Operator Connect customer.

Onboarding Prerequisites

#

Step

Action

System

Documentation  Reference

1

Obtain Program Approval from Microsoft

The Service provider operator must obtain approval from Microsoft to be part of the Operator connect program.
The Service provider operator should have a Azure Tenant subscription with Admin access.

Azure Portal

 

2

Setup AudioCodes Active Directory for OC

Walk operator through how to setup their AAD for Operator Connect.

Azure Portal

 

3

Create App Registration

Service Provider creates an App Registration on their Azure subscription.

Azure Portal

Deploy Synchronization Application

4

Deploy Application to AAD tenant

Walk operator through how to attach the Operator Connect Application in Azure to the AAD tenant and assign Users and Groups.

Azure Portal

Deploy Live Platform Portal Application to Tenant

5

Fill JSON File

The Service Provider configures the information that they wish to display and enable the end customer to configure when they select the Operator in their Teams Admin. For example:

Focal Point Contact details
Countries of Services
Type of numbers (calling, conference etc.)

JSON

Test Access to the Operator Portal

7

Submit JSON File to OC Onboarding Team

Open an ADO ticket and attached the JSON File to load into the system

ADO

Configuring Operator Offerings

8

Add sub-domains to Microsoft 365 portal to match the SBC certificate.

Configure the subdomain FQDN that is configured in the certificate of the SBC trunk in the Microsoft Teams admin center.

Professional Services

Validating the SBC Domain

9

Verify authentication to Live Platform portal.

Verify that you can connect to the portal with the customer operators defined in.Deploy Live Platform Portal Application to Tenant

Multitenant portal

 

10

Validate the SBC Domain

It’s necessary to validate the domain FQDN that is configured in the certificate of the SBC trunk in the Microsoft 365 admin center. This FQDN must also be configured in the DNS server configuration (see below).

Microsoft Admin Center

Validating the SBC Domain

11

Define all Trunks on DNS Server (Configure DNS A-records for each managed SBC device).

Configure Service Provider domain that is used by its’ customers for direct routing registered in Azure DNS, so that it can be configured by the UMP. A record pointing to SBC FQDN should be created for each SBC site location name (Short Customer name).

Azure Portal

Defining all Trunks on DNS Server

12

Configure Teams Trunks (SBC devices)

Configure all SBC devices

Multitenant Portal

Configure Teams Trunk

13

Configure Calling Profiles

The Calling Profiles should be configured including:

Type of supported calling
Deployed SBC devices
Emergency Calling parameters

Multitenant Portal

Viewing Calling Profiles

14

Provide Teams Test Tenant

Provide Onboarder with a maximum of 3 Teams test tenants to be used for pre-production testing.

Email